| Commit message (Collapse) | Author | Age | Files | Lines | 
| | 
| 
| 
| 
| 
|  | 
* use ApprovedCommentProps to make CommentData type
* add the author name of the parent on reply form heading
* add tests
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
* add ApprovedComment, PendingComment and ReplyCommentForm components
* let consumer handle reply form visibility
* move structured data into article page (each article already has the
comments data and already handle json ltd schema so I prefered to move
the schema in the final consumer instead of adding a script element
foreach comment)
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* move Prism styles to Sass placeholders to avoid repeats
* let usePrism consumer define its plugins (remove default ones)
* remove `plugins` prop from Code component
* add new props to Code component to let consumer configure plugins
(and handle plugin list from the given options)
However there are some problems with Prism plugins: line-highlight and
treeview does not seems to be loaded. I don't want to use Babel instead
of SWC so I have no solution for now.
 | 
| | 
| 
| 
| 
| 
|  | 
Instead of using helpers functions to format the date each time we need
to use a time element, it makes more sense to create a new component
dedicated to this task.
 | 
| | 
| 
| 
| 
| 
|  | 
It removes items complexity by allowing consumers to use any label/value
association. Translations should also be defined by the consumer.
Each item can now be configured separately (borders, layout...).
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
The styles applied to ResponsiveImage are related to the figure and
figcaption elements. Those elements could be use with other contents
than images. So I extracted them in a Figure component. The
ResponsiveImage component is no longer useful: the consumer should use
the Image component from `next` and wrap it in a link if needed.
 | 
| | 
| 
| 
| 
| 
| 
|  | 
* Message should be set as children
* Default message is no longer available (depending on use case, the
consumer might prefer aria-label instead)
* It is now possible to define the message position
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
Both:
* move styles to Sass placeholders
Button:
* add `isPressed` prop to Button
* add `isLoading` prop to Button (to differentiate state from
disabled)
ButtonLink:
* replace `external` prop with `isExternal` prop
* replace `href` prop with `to` prop
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
It makes it easier to change a route if needed and it avoid typo
mistakes.
I also refactored a bit the concerned files to be complient with the
new ESlint config. However, I should rewrite the pages to reduce
the number of statements.
 | 
| | 
| 
| 
| 
| 
|  | 
Next expect a default export for pages so only those components should
use default exports. Everything else should use named exports to
reduce the number of import statements.
 | 
| | 
| 
| 
| 
| 
|  | 
Using paths aliases starting with "@" can be confusing and can lead to
conflict with existings modules. I prefer to use relative paths to
avoid extra configuration in tools because of these aliases.
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
Previously, only the first 10 comments was loaded. So I update the
fetching method to retrieve all the comments on a post.
Also, I choose to order comments on client side because of a bug
with WPGraphQL.
Finally, I renamed the Comment type to SingleComment to avoid conflict
with existing types.
 | 
| | 
| 
| 
| 
| 
|  | 
By switching to custom hooks for revalidating articles and comments,
everything was working on development mode but articles failed to build
for production.
 | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
|  | 
By using useSWR I can fetch the changes from the backend.
By using fallback, I can access new articles without rebuilding the
entire app.
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
|  | 
* Improve wp-blocks-columns, wp-block-quote and some images
* Make Sharing widget consistent between pages
* Remove margin option from lists
* Fix Topic logo alignement
 | 
| | 
| 
| 
| 
|  | 
It avoid some hydratation errors on project pages (not in article
however) and the hooks are now reusable.
 | 
| | 
| 
| 
| 
|  | 
It prevents to rerender the common components between pages (header,
footer...).
 | 
| | 
| 
| 
| 
|  | 
* change animation on article card hover
* change comments section alignment
 | 
| | 
| 
| 
| 
| 
|  | 
* add logo to topics pages and links
* add Prism styles to articles
* and a few other adjustements
 | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
Since I'm using new components, I will also rewrite the GraphQL queries
so it is easier to start from scratch.
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
I'm not able to configure SWC plugins in Next.js so to make it works,
all translation must have an id.
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* refactor: replace script tags with next/script
Since next.js v12.1.0 some warnings was displayed because I was using
some script tags.
* build(deps): bump next-themes to v0.1.1
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
Squashed commit of the following:
commit 49c1b3b1556a0eb91c429a961fedd2bded8ffd47
Author: Armand Philippot <git@armandphilippot.com>
Date:   Wed Feb 16 15:17:52 2022 +0100
    chore: add headline field to blogPosting schema
commit 42214c6f032cc899ec252a9387be35dcad738546
Author: Armand Philippot <git@armandphilippot.com>
Date:   Wed Feb 16 15:09:11 2022 +0100
    chore: update the searchAction markup and add query-input
    Google was complaining about "query-input" which is not in Schema.org
    representation. So I added it.
commit 5f29226d937cbdcd262df2793f1588435d850f02
Author: Armand Philippot <git@armandphilippot.com>
Date:   Wed Feb 16 14:32:14 2022 +0100
    chore: remove breadcrumb from homepage
    The breadcrumb is not displayed on the homepage, so the breadcrumb
    field should not appear inside Schema markup.
 | 
| | 
| 
| 
| 
|  | 
The comments list was static before. If an user posted a comment, even
after it was approved, the comments list was keeping the old state.
 | 
| | 
| 
| 
|  | 
I forgot to change the selector to query all code blocks.
 | 
| | 
| 
| 
| 
| 
| 
|  | 
In French, "Utiliser le thème sombre" was a little too long, so instead
I decided to remove the "Toggle" word and add an icon to help user
understand the button purpose.
Same way, "Aucune étoile" was too long, so I replace it with "0 étoile"
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
The translation was not always loaded the first time. So I decided to
put the prism attributes manually instead.
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
I had errors with next build because of fallback. I need to return
early if the path does not exists, if not Next complains about
undefined variables.
I don't think it was related but I also fix the paths format in
getStaticPaths, I forgot the params object in some dynamic routes.
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
The previous method was not working so I tried a different approach.
Translation is loaded but I'm still getting warnings:
* Plurals for locale undefined aren't loaded
* Text content did not match
I can't figure how to fix them...
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
I change the name in graphql endpoint, so I decided to repercute this
change here.
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
I will need the country code, so I think it makes more sense to gather
them inside the same property.
 | 
| | 
| 
| 
|  | 
I also added the featured image on single article.
 |